The problem is that the EAR level BM and module-level BM contain a copy of EjbContainerServices which results in the bean being present twice (in different BMs but hierarchically related).

Solution proposal: register an empty EjbContainerService for modules and delegate EJB resolution to the top-level BM - in EARs.