John, OWB does not need to "support ShrinkWrap procol" at all. SE tests (grouped under org.jboss.cdi.tck.TestGroups.SE) are designed to work with Arqullian SE container adapter which starts a new JVM instance for each test archive so that each test can run with isolated classpath. In other words, ShrinkWrap (together with ClassPath API) is only used to specify the classpath for a test. See also https://github.com/weld/core/blob/master/jboss-tck-runner/pom.xml#L425.

OWB TCK runner needs to define a special profile for SE which adds OWB SE bits to the classpath (similar to the Weld one).