I added the following to the Ejb3Deployment

 /**
 * Return the container injection handler collection. If not specified(null)
 * a default handler collection will be created.
 * @return the injection handler collection to use, null if the container
 * should use a default setup.
 */
 protected Collection<InjectionHandler<Environment>> getHandlers()
 {
 return null;
 }

Sure it could be, but the current contract for the container is rather opaque in terms of the integration layer. The container shows up as an Object in the KernelAbstraction.install call. The Ejb3Deployment is the main integration api for the Ejb3Deployer currently.