Pooled connections memory leaks upgrading past 3.9.4

Using pooled connections, we upgraded from 3.9.4 to 3.11.3 and instantly saw huge memory leaks in many deployed production enviroments. See screenshots below from google cloud run where the line with the i and dotted lines marks the deployment of the libary 3.11.3. Its very clear that its the changes between 3.9.4 and 3.11.3

Screenshot of container insights in production after deployement

I downgraded to 3.9.7 and still have the memory leaks.

Rolling back to mysql 3.9.4 solves the issue

We are using typeorm but the mysql config parms are just passed down. I will write the relevant ones below;

{
          type: xxxx,
          username: xxxx,
          password: xxxx,
          database: xxxx,
          entities: dmsDbEntities,
          synchronize: false,
          pool: {
            max: 25,
            min: 0,
          },
          extra = {
            socketPath: /xxxx/x 
          }
        }

No source file or test is named. Start by reproducing the reported upgrade from 3.9.4 with pooled connections, the shown max/min pool settings, and socketPath configuration, then compare behavior through 3.11.3 and 3.9.7. Done means the memory leak is isolated and a regression test or focused reproduction demonstrates the corrected behavior.