Hi,
when it comes to CDI Lite, the intent is that Lite is a strict subset of Full. Lite includes the new extension API (provisionally called Build Compatible Extensions). Full includes both Portable Extensions and Build Compatible Extensions (because it includes complete Lite). We didn't want to mess with Weld internals to support 2 extension APIs, so the new extension API is implemented as a standalone Portable Extension. That is the "adaptor" Scott mentions.
The way I see it, Weld would always include this adaptor, because that's the only way for it to be compliant. So that's not something that would have to be integrated on the WildFly level (except perhaps making sure that the Portable Extension is "discovered" -- not sure if that's necessary).
Again, given that Lite is a strict subset of Full, Weld implementing Full should very much be compliant with Lite. If the Core Profile demands CDI Lite, it is my opinion that an implementation supporting CDI Full should be just fine.
LT