And MDB using a run-as role along a call path:
DeepRunAsMDB -> Level1MDBCallerBean.callEcho() ->
Level2CallerBean.invokeEcho() -> Level3CalleeBean.echo()

properly uses the run-as role for access to the ejbs, but we have a weaker notion in 3.2 vs 4.0 of how the run-as should show up in the isCallerInRole context call, and this test validates that the run-as role is seen by isCallerInRole. The 3.2 implementation needs to be updated to support this as well.