This affects:
EjbRemoveUnitTestCase.testEjbRemoveCalledForEveryCall: https://github.com/jbossas/jboss-eap7/blob/EAP_7.1.0.CR1-dev/testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/ejb/stateless/pooling/ejb2/EjbRemoveUnitTestCase.java#L126

LifecycleTestCase.testStatelessBeanLifecyleCallback: https://github.com/jbossas/jboss-eap7/blob/EAP_7.1.0.CR1-dev/testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/ejb/security/LifecycleTestCase.java#L163

We should decide what to do with 'em. Options:

• fix them by applying the necessary config changes - explicitly disable SLSB pooling before the test
• remove them

My vote is for removing them, for two reasons:

• disabling SLSB pooling does not quite seem a real-world reasonable use case for me, so the benefit from having these tests is quite poor
• the needed config change requires server reload, which slows down the TS execution and has been known to cause instabilities