We have just deployed multiple Access Manager environments behind a pair of CSS 11503 for redundancy. The CSS's are configured inline with a pair of 6513's. We have also done this with the older Local Director LD416.
In general to configure WebSEAL behind a load balancer. Setup a virtual address on the front side of the load balancer. This will be the address you will tunnel or nat all the outside traffic to.
Bind the Virtual Address to the address(es) of the WebSEAL servers. In order to keep session state use an IP sticky mode. Otherwise unless you have failover cookies setup, the remote user will loose their session when they come back into the site on another connection.
Then use a single WebSEAL junction with multiple servers to load balance backend resources.
Allow through what ever ports WebSEAL is configured to listen on, usually 80/443, on the front side.
In general it will be internet -> PIX -> 6513 -> CSS -> WebSEAL -> webservers.