The support requested by Ben is to support the usage of DeltaSpike Config. In DeltaSpile Config, it uses TCCL to work out the configuration sources the TCCL can see and then get hold of the configurations.

In myear,
warA: MyExtensionA to observe BeforeBeanDiscovery
warB: MyExtensionB to observe BeforeBeanDiscovery

The extensions try to get TCCL and then use Config api to get hold the config object (e.g. ConfigProvider.getConfig(tccl)). Since the extensions are started on application starting, there is only one thread. It is impossible for the integrator to set multiple TCCLs for multiple war cases. By the way, the issue reported in this jira occurs in Wildfly.

Since Weld starts all extensions, it has the correct classloader to start the extension. It can set that on the thread. When it finishes, it removes it.