Grails 3.3.11 consumes 100% CPU if is running in a different port (jvmArgs '-Dserver.port=8090')

### Task List

- [x] Steps to reproduce provided
- [ ] Stacktrace (if present) provided
- [x] Example that reproduces the problem uploaded to Github
- [x] Full description of the issue provided (see below)

### Steps to Reproduce

1. Create a new Grails 3.3.11 application.

2. Inside build.gradle change:
`jvmArgs('-Dspring.output.ansi.enabled=always')`
to
`jvmArgs('-Dspring.output.ansi.enabled=always', '-Dserver.port=8090')`

3. Execute `grails run-app`

### Expected Behaviour

The application should run fine.

### Actual Behaviour

Application consumes 100% CPU.

### Environment Information

- **Operating System**: Linux Mint 19.2 Tina x86_64 (Kernel: 4.15.0-101-generic)
- **Grails Version:** 3.3.11
- **JDK Version:** Oracle jdk1.8.0_251

### Example Application

- https://github.com/lamon/grails3311-different-port : link to github repository with example that reproduces the issue

Start by running the reproduction steps from the issue with the linked example application and inspect build.gradle around the jvmArgs configuration. Compare behavior with and without -Dserver.port=8090, then trace the grails run-app startup path to identify the source of the CPU loop. Done means the application starts on port 8090 without consuming 100% CPU.

Written by the indexing model from the issue text.