Erick -
Sorry, no. Unfortunately there is nothing a GeoEvent administrator can do to work around the issue. It's not a resource leak that can be addressed with a server / service restart for example. The implementation of the TCP transport when running as "mode=CLIENT" is simply pinging the server hosting the socket connection too frequently - which is why the CPU resource is spiking.
The fix was implemented for the 10.3.1 product release which should be publically available mid-May 2015. We did back-port a product hot-fix for for the 10.3 product release. I would encourage you to upgrade to 10.3.1 as soon as it's available, but if that's not an option for you, please contact your customer service representative and request the hot-fix. (Hot fixes may be specific to a customer's environment which is why they are not distributed more generally as, say, a product patch would be.)
- RJ