Service providers may have observer methods, which may observe any event, including any container lifecycle event, and
obtain an injected BeanManager reference.

It's probably a failure to inject BeanManager in BeforeBeanDiscovery which causes https://issues.apache.org/jira/browse/TOMEE-33

Currently, the TCK tests the BM injection for the following types of events:

• AfterBeanDiscovery
• AfterDeploymentValidation

We should extend the coverage and test every kind of container lifecycle event (BeforeBeanDiscovery, ProcessAnnotatedType, ...).