Restarting Node Configuration from UI causes communication channel to master to be broken

If I restart a node configuration from the UI (Node -> Node Configuration -> Restart), the node shuts down as seen in the node's log but also causes the communication channel from the slave to the master to be broken. See below log snapshot:

09:36:07.242 INFO - Stopping Acceptor ServerSocket[addr=0.0.0.0/0.0.0.0,localport=4445]
09:36:07.341 INFO - Stopped SocketListener on 0.0.0.0:4445
09:36:07.431 INFO - Stopped HttpContext[/selenium-server,/selenium-server]
09:36:07.433 INFO - Stopped org.openqa.jetty.jetty.servlet.ServletHandler@6ebd2c64
09:36:07.514 INFO - Stopped HttpContext[/wd,/wd]
09:36:07.577 INFO - Stopped HttpContext[/selenium-server/driver,/selenium-server/driver]
09:36:07.607 INFO - Stopped HttpContext[/,/]
09:36:07.608 INFO - Stopped org.openqa.jetty.jetty.Server@5e119c63
channel stopped

After the channel stopped, there is nothing else coming from the slave in terms of communication even if the slave is still running and connected. This is only seen on Windows slaves at the moment, I have not tried with other types of slaves.