New keyboard shortcut permanently hides running / debugging job

This behavior appears to be new in 2016.3, but it's possible I just never noticed it before. It's screwed me up three times today, though. This is on OS X but I assume the experience on other platforms is similar.

Steps:

1. Run a job in debug mode OR run mode; doesn't matter. This should be a long-running job, like a server.

2. Hit [cmd]+W

3. The tab for the running process is gone -- there is no way to recover it. However, it is NOT stopped. As far as I know the only way to get at it is to kill it from the terminal (undesirable).

Is it a known bug? Surely this can't be intended behavior.

Confirmed that this is the same shortcut as for closing a file in the editor tab, meaning you either have both or neither. This shortcut makes sense for files (and I use it all the time) but is problematic for tasks, as (a) you rarely want to close a task while it's still running, without stopping it, and (b) there's no way to cleanly reopen a closed task, unlike with files.