The problem isn't with SQL server itself. That's actually on a different server. The problem I'm having is with the DBI proxy process that is located on a server by itself.
After each connection the size of the memory taken by the perl process grows by about 3-4 megs and the memory is never given back to the OS after the linux client disconnects from the proxy. So after running for awhile, the perl process ends up taking up 150 megs or more of memory and then stops responding. At that point the process has to be killed and restarted to free the memory and get the process working again.