[BUG] Testing with jest using more and more heap memory.
## Information

- **Version:** 7.14
- Packages: 
``` "dependencies": {
    "@tsed/ajv": "^7.14.0",
    "@tsed/common": "^7.14.0",
    "@tsed/core": "^7.14.0",
    "@tsed/di": "^7.14.0",
    "@tsed/engines": "^7.14.0",
    "@tsed/exceptions": "^7.14.0",
    "@tsed/json-mapper": "^7.14.0",
    "@tsed/logger": "^6.3.4",
    "@tsed/logger-file": "^6.3.4",
    "@tsed/platform-cache": "^7.14.0",
    "@tsed/platform-exceptions": "^7.14.0",
    "@tsed/platform-express": "^7.14.0",
    "@tsed/platform-log-middleware": "^7.14.0",
    "@tsed/platform-middlewares": "^7.14.0",
    "@tsed/platform-params": "^7.14.0",
    "@tsed/platform-response-filter": "^7.14.0",
    "@tsed/platform-views": "^7.14.0",
    "@tsed/schema": "^7.14.0",
    "@tsed/swagger": "^7.14.0",
    "ajv": "^8.12.0",
    "barrelsby": "^2.5.1",
    "body-parser": "^1.20.1",
    "compression": "^1.7.4",
    "cookie-parser": "^1.4.6",
    "cors": "^2.8.5",
    "cross-env": "^7.0.3",
    "dotenv": "^16.0.3",
    "dotenv-expand": "^10.0.0",
    "dotenv-flow": "^3.2.0",
    "express": "^4.18.2",
    "method-override": "^3.0.0"
  },
  "devDependencies": {
    "@babel/cli": "^7.20.7",
    "@babel/core": "^7.20.12",
    "@babel/node": "^7.20.7",
    "@babel/plugin-proposal-class-properties": "^7.18.6",
    "@babel/plugin-proposal-decorators": "^7.20.13",
    "@babel/preset-env": "^7.20.2",
    "@babel/preset-typescript": "^7.18.6",
    "@tsed/cli-plugin-eslint": "4.2.2",
    "@tsed/cli-plugin-jest": "4.2.2",
    "@tsed/components-scan": "^7.10.0",
    "@types/compression": "^1.7.2",
    "@types/cookie-parser": "^1.4.3",
    "@types/cors": "^2.8.13",
    "@types/express": "^4.17.17",
    "@types/jest": "^29.4.0",
    "@types/method-override": "^0.0.32",
    "@types/multer": "^1.4.7",
    "@types/node": "^18.13.0",
    "@types/supertest": "^2.0.12",
    "@typescript-eslint/eslint-plugin": "^5.51.0",
    "@typescript-eslint/parser": "^5.51.0",
    "babel-plugin-transform-typescript-metadata": "^0.3.2",
    "babel-watch": "^7.7.2",
    "eslint": "^8.33.0",
    "eslint-config-prettier": "^8.6.0",
    "eslint-plugin-prettier": "^4.2.1",
    "jest": "^29.4.2",
    "supertest": "^6.3.3",
    "ts-jest": "^29.0.5",
    "ts-node": "^10.9.1",
    "tsconfig-paths": "^4.1.2",
    "tslib": "^2.5.0",
    "typescript": "^4.9.5"
  },
```

First I'd like to thank everyone involved in this very cool framework. The reason I'm createing this issue is because me and my team stumbled on a problem after adding ~500 tests most of them intergration tests.

We're getting the following error in our pipelines:
```FATAL ERROR: MarkCompactCollector: young object promotion failed Allocation failed - JavaScript heap out of memory```.

To test if same issue occurs on a new project I've created an unmodofied projectwith `tsed init .` command. Below are the options I've chosen:
? Choose the target platform: **Express.js**
? Choose the architecture for your project: **Ts.ED**
? Choose the convention file styling: **Ts.ED**
? Check the features needed for your project **Swagger, Testing, Linter, Bundler**
? Choose unit framework **Jest**
? Choose linter tools framework **EsLint**
? Choose extra linter tools 
? Choose your bundler (Use arrow keys)
❯ **Babel** 

After installing `components-scan` I've tried running `node --expose-gc ./node_modules/.bin/jest --logHeapUsage --detect-leaks` without any modification to tests created on `init`.

It returns that the default tests are leaking:

```
EXPERIMENTAL FEATURE!
    Your test suite is leaking memory. Please ensure all references are cleaned.

    There is a number of things that can leak memory:
      - Async operations that have not finished (e.g. fs.readFile).
      - Timers not properly mocked (e.g. setInterval, setTimeout).
      - Keeping references to the global scope.

      at onResult (node_modules/@jest/core/build/TestScheduler.js:150:18)
      at node_modules/@jest/core/build/TestScheduler.js:254:19
      at node_modules/emittery/index.js:363:13
          at Array.map (<anonymous>)
      at Emittery.emit (node_modules/emittery/index.js:361:23)

```

Even without `--detect-leaks` you can observe heap size growing with every test that bootstraps Server application.
```
 PASS  src/controllers/rest/HelloWorldController.spec.ts (160 MB heap size)
 PASS  src/Server.integration.spec.ts (209 MB heap size)
 PASS  src/controllers/rest/HelloWorldController.integration.spec.ts (209 MB heap size)
```

Do you know about this issue and maybe have a solution we could implement?
