All synthetic beans coming from portable extensions are registered under the extension that triggered the addition.
In case of BCE, this isn't true because we effectively execute all BCE from LiteExtensionTranslator. Therefore, all synth. beans from BCE will be seemingly coming from there.

This is mostly fine (albeit confusing), however it can mess up use cases where users try to register synth beans and use the variant where you get Instance<Object> and can dynamically resolve beans. In such case, the dynamic resolution can fail because the BeanManager used to obtain Instance comes from an archive that LiteExtensionTranslator belongs to - and due to possible bean visibility restriction in EE environments, this might result in unsatisfied dependencies.