When starting embeddable glassfish within a unit test (JUnit 4.7), weld does only register managed beans
(CDI-beans) discovered in the same bean archive as the EJB:s. If an EJB depend on (via @Inject or @Inject +
@SomeQualifier) a bean in another bean archive, start-up of the container fails with
"org.glassfish.deployment.common.DeploymentException: Injection point has unstatisfied dependencies.
Injection point:...". It does however successfully load the classes into the JVM: Removing the @Inject-
annotation makes the container launch, but - of cause - some tests to fail.
I raised it as a blocker, since I'm not aware of a work-around.