Order of which hst components are loaded influence the inheritance where this should not be the case

We ran into what looks like inconsistent behaviour of the HST between
a component container directly defining a class and template, and a
component container referencing a component configuration defining the
exact same class and template.

Take the following configuration:

• hst:pages

  – default
  -- main [template: default.main]
  	– content [componentclass:org.example.Content, template: default.main.content]
  -- sidebar
  – foo [referencecomponent: hst:pages/default]
  -- main [template: default.main]
  	– content [componentclass:org.example.MyComponent, template:mycomponent]
  – bar [referencecomponent: hst:pages/default]
  -- main [template: default.main]
  -- content [referencecomponent: hst:components/mycomponent]

• hst:components
  -- mycomponent [componentclass:org.example.MyComponent, template:mycomponent]

One would expect the resulting pages for 'foo' and 'bar' to be exactly
the same. However, 'foo' results in the expected page (using
mycomponent), but 'bar' results in the page one would expect for the
'default' page configuration (using the org.example.Content class and
default.main.content template).

Is this a bug?

Thanks,
Niels