Both protocols use the same "jgroups.nio.server" name (since they both use NioServer class, which hard-codes this value).
The side effect of this is that WildFly's socket binding manager reports the incorrect socket used by one of these protocols (depending on which last created its socket).
This can be fixed easily enough by adding a service_name parameter to the NioServer constructor.