The 'console-enabled' attribute on the /core-service=management/management-interface=http-interface' resource defaults to a value of true, but the 'management' Galleon layer that adds that resource does not ensure the 'org.jboss.as.console' package is provisioned.  Provisioning the package requires use of the 'web-console' Galleon layer.

The effect is that in slimmed-server scenarios it is easy to end up with an installation that produces this log warn:

10:55:02,888 WARN  [org.jboss.as.domain.http.api.undertow] (MSC service thread 1-1) WFLYDMHTTP0003: Unable to load console module for slot main, disabling console' 

The 'web-console' layer is not part of any other layers other than the 'internal' ones that produce the OOTB configs, so this WARN can readily occur.

In a perfect world the 'management' layer would set console-enabled to false and web-console would set it to true, at provisioning time the web-console setting would win, and, furthermore, all OOTB config files (including host.xml variants) would end up with a setting whose runtime effect is equivalent to what they have now.

NOTE: The fix for this will likely involve changes to full WF, so I filed WFLY-20748 as well.