I have also tested the issue and would like to share some observations that might help to fix it:

  1. once any EJB decorator is activated in container (over @Inject) also the non-CDI invocations will trigger the EJB decorator
  2. using a SPI extension like: public void afterBeanDiscovery(@Observes AfterBeanDiscovery event, BeanManager manager) and inspecting the decorators over manager.resolveDecorators(...) the EJB decorator activated over the non-CDI invocation is not known to the manager.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira