Fix the native-memory leak in server response compression. With the default compression setting enabled, an HTTP client can disconnect after receiving the first part of a compressed response; the zlib context associated with that unfinished response must then be closed and released promptly instead of surviving garbage collection and permanently retaining its deflate state. The fix must cover all requests that pass through Next.js server routing, including production, development, and custom-server usage. Preserve existing behavior for responses that finish normally: gzip responses must still decode to the complete byte-identical payload. Cleanup must also remain safe when compression is disabled or was not activated for a response, without throwing or leaving response listeners behind.