Martin Kouba Tomas Remes I am not sure this is doable for master branch in such a broad way - please correct me if I am wrong.
The reason is that Weld 3 brings in more changes to WFLY internals and hence requires recompiling of, for instance, org/jboss/as/weld module.
We simply do not have that JAR at hand to put it there and patch WFLY (and subsequently create patch file).

Also, the update script has been thus far used with existing Weld 3 WFLY upon which you forced newer version - again there you had the internals updated already.
If I am not mistaken then all I can add here at the moment is:
1) download of pristine WFLY
2) creation of patch file on the assumption that you yourself provide the patched WFLY

Alternative (crazy) version would be to download our own patch we deliver and use it to patch the pristine WFLY and go from there. This should be theoretically possible but we would be patching a patched server
I'd like to hear your preferences on this.