As Chris suggests, a OneConnect profile is definitely the way to correct this behavior. It's not really a bug per se. It's due to the default connection based load balancing.
If you're using a SNAT to translate the source address on serverside connections, you can use the default OneConnect profile with a 0.0.0.0 source mask. If you're preserving the original client IP address on serverside connections, create a custom OneConnect profile with a source mask of 255.255.255.255.
OneConnect
http://devcentral.f5.com/wiki/default.aspx/AdvDesignConfig/oneconnect.html
Aaron