jfisherdev reports at https://wildfly.zulipchat.com/#narrow/stream/196266-wildfly-user/topic/WildFly.2022.20client.20geronimo-json.20conflict :

"It looks like in the 22 version of the wildfly-jms-client-bom and wildfly-client-all artifact that the geronimo-json_1.0_spec-1.0-alpha-1.jar is not being excluded from the org.apache.activemq:artemis-commons dependency, which appears to have introduced a dependency on org.apache.geronimo.specs:geronimo-json_1.0_spec:1.0-alpha-1 in the update from 2.10.1 to 2.16.0 and is now being targeted in 22.

The consequence of this is that it introduces conflicting/incompatible versions of javax.json API classes with the proper jakarta.json:jakarta-json-api and org.glassfish:jakarta.json artifacts the bundle targets. More specifically for the wildfly-client-all.jar artifact it causes the javax.json classes to be replaced with those from the geronimo-json spec JAR. If you have a client app that happens to use javax.json APIs and includes the wildfly-client-all.jar [also a possibility with the BOM for Maven clients that don't explicitly manage the conflict], you can encounter various issues as I noted in the forum post."

Forum thread is at https://groups.google.com/g/wildfly/c/VugE1NzIwfc