EJB run-as identity gets lost if an unsecured ejb in the call stack - not fixed in Elytron

Follow up to JBEAP-11462, because this issue doesn't seem to be resolved in the case where Elytron is used.

To reproduce, use the same steps as in JBEAP-11462, but instead of creating a jmx-console security domain, create an application-security-domain mapping from jmx-console to ApplicationDomain Elytron domain.