So to generically use the Ejb3ClientDeployer, it needs to output the BeanMetaData instead of trying to install it so that the resolving deployer can properly setup the dependencies based on the resolved target. Handlers like the EJBHandler are assuming an ejb3 target, which is not correct in general. The current failure of the ClientENCInjectionContainer to start for most deployments is because of invalid dependency creation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100070#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...