The following TCK tests,

testInjectionOfDependentPrimitiveProductIntoNormalBean
testInjectionOfDependentSerializableProductIntoNormalBean
testNonSerializableProducerFieldDeclaredPassivatingThrowsIllegalProductException
testPassivatingScopeProducerMethodReturnsUnserializableObjectNotOk

related to the EAR,

org.jboss.jsr299.tck.tests.context.passivating.PassivatingContextTest.ear

fail with the following exception in GF v3,

attached to this wiki [1] which generates the following exception when deployed:
java.lang.RuntimeException: by java.lang.IllegalAccessError: class org.jboss.jsr299.tck.tests.context.passivating.NumberConsumer_$$_javassist_389 cannot access its superclass org.jboss.jsr299.tck.tests.context.passivating.NumberConsumer
at javassist.util.proxy.ProxyFactory.createClass3(ProxyFactory.java:344)
at javassist.util.proxy.ProxyFactory.createClass2(ProxyFactory.java:314)
at javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:273)
at org.jboss.weld.util.Proxies.createProxyClass(Proxies.java:153)
at org.jboss.weld.util.Proxies.createProxy(Proxies.java:136)

The reason for this failure is that the WAR in the EAR above does not include a Class-Path entry in its manifest to be able to load classes from the JAR. This manifest entry is required for portability. Note that GF v3 now uses the TCCL with Javassist.