ISSUE_27: fix EAR deployment isolation + introduce bug for ISSUE_28

Isolate EJBs deployed in EARs, just like EAP5 does - NOTE: it is possible to deploy same EJBs as part of two EARs, but two JARs/WARs will collide.


BUG: EJB registry in EAP5 is MC based, hence there is magic handling name conversion on bind to ObjectName. ON is used as lookup target from EJB code. In our case it makes us look for Metadata.containerName -> which is ServiceName, in registry which has name like "ProxyFactory/my-ear/EjbInterface". Code version prior this commit was handling ContainerName badly, fix to that made this bug to popup:

https://github.com/baranowb/jboss-as-legacy/compare/ISSUE_27?expand=1#diff-373b3ddd1f591e18bde868d34cb1258bL125
https://github.com/baranowb/jboss-as-legacy/compare/ISSUE_27?expand=1#diff-373b3ddd1f591e18bde868d34cb1258bR218