We must not break backwards compatibility. The tests where passing before, so the should keep on passing without changes. Any CP release is a drop-in replacement.
The implementation in EAP 4.2 does not conform to specifications. This is a known issue and should not be addressed. The implementation is provided as is.
(So there can be no bugs in EAP 4.2. ;-) )
We fixed the implementation to work with spec (hopefully covers all cases) for the Beta3 release...merging those changes into 4.2 will break existing apps.
What change made these tests in 4.2 fail now? Ping me if you want another eye; I spent awhile on this for 5.0.0.x.
OK, I'll roll back my changes to the tests. Somehow the Beta3 changes made it into EAP 4.2 CP02 or we broke it in a very similar way. Shouldn't be a major fix - we're just not implementing EJBObject/EJBLocalObject in the proxies unless they are explicitly extended by the interfaces.