Noticed this in production. http2 compat response doesn't always emit `'close'` which can cause a memory leak. Not sure yet when/how this occurs. Suspect that it occurs when the client aborts a request.