Grafana dashboards indicate a continuous increase in the Goroutine count within the Vault service. <img width="1181" height="580" alt="Image" src="https://github.com/user-attachments/assets/f42bb443-02e9-45bc-ad3d-1d82e5ec398f" /> A subsequent pprof analysis revealed a significant number of persistent HTTP connections that are not being closed. <img width="1392" height="561" alt="Image" src="https://github.com/user-attachments/assets/2cdc728d-034d-46f6-a280-fe66394cd779" /> These connections all originate from and are directed towards Elasticsearch. <img width="1504" height="1412" alt="Image" src="https://github.com/user-attachments/assets/c679e4df-9821-4f37-bde5-d7f8ac9bdbdf" /> The [buildClient function](https://github.com/hashicorp/vault-plugin-database-elasticsearch/blob/main/elasticsearch.go#L286) is used for all Elasticsearch calls, but its connection pool is only configured with TLSClientConfig. Vault Version:1.14