As a consequence of hitting JBIDE-11989 I found another problem. If for whatever reason the server fails to start properly (e.g. -Djboss.bind.address.management set to null) this is what happens:
1. The process keeps running on the remote host
2. The server is in Starting state until it reaches time out
3. This is where remote and local servers differ, but both behave wrongly
3.a - remote server: When time out is reached, server stops, but the process keeps running - you have to kill it manually
3.b - local server: When time out is reached, server tries to stop, but fails doing so. So you have to force stop and then it stops and the process is killed.

The the bigger problem is with remote servers - you have no way of stopping the server other than sshing to the server and killing the process.
In the case of local server, it is not so bad, but still after the time out the tools should be able to stop the server on first attempt.