Syslog and TCP

I'm looking for a solution to this as well.  We need to be able to use the F5 as a load balancer for TCP Syslog, as some sources are very chatty, and overwhelm the connection that persists to a single server.

We would prefer that traffic be load balanced across the pool members, round-robin style, for each syslog packet.

1) Can the F5 determine when a syslog packet ends?

2) If #1 is true, then we need to be able to send 33% of the Syslog packets to each of the three pool members?

We can do iRules, but we need to be able to handle 300,000 EPS, during our busy hours.