The legacy-xx boms introduced in WFLY-16660 declare all the artifacts that were being used at the time to build the javax.* standard WildFly. But following WFLY-16652 all that's really needed are deps needed to either

1) build the legacy javax.* maven modules (including running those modules own tests)

2) Run testsuite modules that use legacy dependencies on the client side (I believe only testsuite/integration/legacy and testsuite/integration/legacy-ejb-client.)

Other dependencyManagement entries not needed for these uses can be removed.

One possible way to do this is to use an empty maven repo and build the server with -DallTests (including running the tests). When its done if a dependencyManagement entry doesn't match with something found in the repo it wasn't used and can be pruned.

(Instead of -DallTests it's probably simpler to just confirm that testsuite/integration/legacy and testsuite/integration/legacy-ejb-client are the only ts modules that need to run.)