Windows Service Bus - MessageBroker service and heavy cpu usage

When sending messages to a (default configured) Topic and receiving messages via a Subscription... the Microsoft.ServiceBus.MessageBroker.exe service eventually uses all available cpu, making the server unresponsive.  The service also uses an exceptionally large amount of ram, and doesn't release.

STR

1. Install and configure Windows Service Bus onto a single-instance (Windows Server 2012r2 VM, 4-procs, 10-gigs ram)
2. Create a Topic and Subscription - or a Queue
3. Send 100,000 messages to the Topic or Queue
4. Receive all messages either simultaneously or after sending is completed

RESULT

• Microsoft.ServiceBus.MessageBroker.exe service consumes 4-5 gigabytes of ram and never releases.
• After all messages are sent and received, Microsoft.ServiceBus.MessageBroker.exe service appears to perform maintenance tasks, and the service utilizes all available cpu for about 1-hour.