From what I have read, this is an issue with .NET Entity Framework not releasing connections to the database. The developers are searching the application code to see if they can find the issue but in the mean time, is there anything I can do on the DB side to help with this?
Have you tried this ( increase number of statement handles to applications) ?
How much memory does your Windows system have ?
Note that CLIPkg is by default 3 and use caution when increasing the amount of packages as each package uses considerable amount of memory and resources.
https://datageek.blog/2013/09/04/binding-packages/ (see the section on CLIPKG issues )