All, It looks like the logic in BeanManagerProvider doesn't work when there are multiple classloaders in play. This came up in DELTASPIKE-782 where you cannot resolve a bean from within a servlet (because the servlet is in the webapp classloader and not the app loader). This seems to impact the SE features more than anything, since containers can use JNDI to look up a bean manager.
It looks like there was a check at some point that parent classloader may give a null BMI, however that never happens since it gets instantiated and put in the map regardless. See here: https://github.com/apache/deltaspike/blob/master/deltaspike/core/api/src/main/java/org/apache/deltaspike/core/api/provider/BeanManagerProvider.java#L402 John
