It's related to the @Init change and needs a bit of investigation. The test case looks valid so might be an edge case which was missed out (the test deployment doesn't explicitly have a @Init marked for ejbCreate() for EJB2.x view). I'll take a detailed look some time later.