DefaultMcpTransportSession#closeGracefully leaks resources on incomplete DELETE response

[1256064203]

Bug description
When the MCP server is abnormal, the statement this.onClose.apply(this.sessionId.get()) in the closeGracefully method of DefaultMcpTransportSession.java throws an exception, so this.openConnections::dispose is never executed and may leak resources.

Environment
Java version: 21
mcp-bom: 0.11.3

Steps to reproduce
1、Create an McpSyncClient.
2、Execute client.initialize(); client.listTools();
3、Suspend the debugger at client.closeGracefully();
4、Make the MCP server unavailable.
5、Resume execution of client.closeGracefully();

Expected behavior
this.openConnections::dispose should always be executed.

Minimal Complete Reproducible example
McpSyncClient client = McpClient.sync(transport)
.requestTimeout(Duration.ofSeconds(10))
.build();

// Initialize connection
client.initialize();

// List available tools
ListToolsResult tools = client.listTools();

// Close client
client.closeGracefully();

[JunJieLiu51520]

Can you take a screenshot of the leaked stack trace? from this code, i think it won't be happed

[CnLight]

this worker will be close but selector always running, the way of close can not shutdown the httpclient

[chemicL]

Is this perhaps related to the inability to close the HttpClient properly in Java 17?

[chemicL]

An estensive analysis was published in the duplicate issue: #620 (comment)