What is the differences between mod_cluster "stop" and "disable" ?

Issue

• Is the documentation mistaken on mod_cluster-manager for stop/disable ?
  • Refer to: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Operations_Network/3.0/html/Manage_JBoss_Servers/mod_cluster.html
  • (Stop allows the webapp context to drain before removing it from the load-balancing, so this essentially shuts down the webapp gracefully. It can take several minutes or even hours for the webapp context to stop. Disabling a webapp context immediately removes it from load balancing.)
• But when we try using /mod_cluster-manager UI to stop/disable, the behaviour seems to be exactly opposite. Stopping a context abruptly stop forwarding to a node, while disabling a context still allow traffic to continue.