Given the proxying strategy documented in the CDI specification, normal scoped beans get initialize when an injected proxy reference is first called.
While that's perfectly fine in the vast majority of use cases, that proves inconvenient when dealing with ApplicationScoped beans that capture application singletons which we want to bound to the application lifecycle with a postConstruct callback. As this callback is only called when a proxy is invoked, it is frequent to see the application developers using a CDI extension to meet that need, e.g.:
There should be a concise way to declare that intent which would then be address by the CDI container, for example: