Potential Issue: internal message handlers run in uncontrolled goroutines

[OrMemphis]

Current behavior

the broker is subscribing to "memphis" sdk requests, when a message arrives a handler is invoked in a new goroutine. Thus, a decent amount of these requests can potentially deteriorate the broker's performance

Suggested solution

Consider using a goroutine pool with a predetermined limit for the amount of goroutines

maybe use tunny

Additional context

No response

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

Contributing Docs

• [x] I agree to follow this project's Contribution Docs