Ah, ok. Thanks for clarifying. No, I think you're stuck with the per-session pool behavior you're currently seeing. To be quite honest though, given a long enough curve, won't it all theoretically balance out?
If you are balancing across divergent paths (different ISPs or even POPs), per-flow loadbalancing is better anyway, especially for TCP.
-d
