Without this, an open request could hang if a prior connection was not
explicitly close()d but instead allowed to go out of scope.
The spec says that the dangling connection should be closed when the
execution context it was opened in is destroyed, but no other browser
does so. Detecting the execution context being destroyed would likely
mean a lot of overhead in JS calls, so it's best to avoid that, despite
this being observable.
61b9be47ce