Load balancing effect on ssh/https connections

Question

We have a RV016 load balancing between two broadband WAN connections. On protocols that are sensitive to a change in IP address such as ssh and https, if the client connection goes inactive for a short time (sometimes as short as 10 seconds), the RV016 often changes WAN connection as part of its "load balancing" feature. Most protocols do not even notice, but the more sensitive protocols do and often lock a session or timeout the session which is not a good thing.
We have been able to bind these sensitive protcolols to a particular WAN port but (in our minds) this is not an "ideal" situation. In fact I would consider this to be a broken "load balancing" solution and should be fixed.
Does anyone have any "permanent fixes" or ideas on this?
Thanks!

Answer 1

Sorry Tom, but I wrote (edited for clarity): "What would happen [..] when the particular WAN chosen goes down? Does the system apply the same binding to ***another WAN*** until the original one comes back up, will it ignore the bining and so break any new sessions of the same protocol or will it simply fail (no connection)?"
I did not write "the other WAN". That is, I am considering the case, quite common, of more than two WANs.
Proper load balancing is described here:
http://help.mysonicwall.com/sw/eng/305/ui2/23100/Network/WAN_Failover_Load_Balancing.htm
"About Source and Destination IP Address Binding
When you establish a connection with a WAN, you can create multiple interfaces, dividing up the task load over these interfaces. There are both Primary and Secondary WAN interfaces. This task distribution model maintains high performance, ensuring that one interface does not become an impasse to the point where it blocks traffic from passing. This process is WAN Load Balancing.
While WAN Load Balancing addresses performance challenges, it can create other problems, including losing track of sessions. Session confusion can occur because some applications fail to adequately track multiple user sessions load-balanced on multiple interfaces. These applications treat incoming packets as originating from different users because they use IP addresses to differentiate user sessions instead of application-layer user identification tags.
To ensure that you have proper connectivity in all applications, SonicWALL provides a feature called Source and Destination IP Addresses Binding, a solution that maintains a consistent mapping of traffic flows with a single outbound WAN interface."
and their appliances are no more expensive than Cisco multi WAN ones...