https://github.com/jboss-modules/jboss-modules/pull/233 introduced the idea of providing a "java.se" module right from the JBoss Modules project. The implication of this is that the Java runtime doesn't have to explicitly --add-modules=java.se and yet the JBoss Modules runtime can still provide a "java.se" module dependency.
The implementation of this, adds DependencySpec(s) of Java modules, that "java.se" module "requires". Right now, this list is hardcoded within the code https://github.com/jboss-modules/jboss-modules/blob/1.9/src/main/java/org/jboss/modules/JavaSeDeps.java#L12. As a result, any new Java modules that have been added as "requires" of "java.se" module, in newer versions of Java aren't taken into account.
Consider the example of "java.net.http" module which is now required by the "java.se" module in Java 11. If an application running on Java 11 adds a dependency on "java.se", right now, it runs into a ClassNotFoundException if it tries to load the classes belonging to "java.net.http" module.