No need for explicit closing: WebClient is thread-safe and does not require explicit closing, as it is managed by Reactor Netty. There is no need to close it unless you are using custom resources.

Connection management in Reactor Netty: If you are using the standard WebClient, resources and connection pool are managed automatically. For custom resources, such as ConnectionProvider, they must be closed manually when the application is terminated.

Recommendations for long-lived applications: For Telegram bots, create one instance of WebClient, reuse it, and configure connection parameters via ConnectionProvider if necessary.