The fact that two or more Windows hosts cannot successfully access the same volume at the same time is not something that's limited by this particular hardware. As you've already discovered, you will get corruption if you configure the system with more than one server to access the same volume _unless_ you use a locking mechanism. This is what MS Cluster service is; it locks the volume to one particualar host at any one time.
The hardware as such will happily share the volume(s) to multiple hosts, it's simply a matter of checking the wwids in the ACU utility.
For two or more hosts to have concurrent access to the same volume, the file system must be aware of this. NTFS is simply not designed around it. Therefore, not many applications could benifit from it either, unless they were highly specialized to take advantage of the concurrent access. Oracle RAC is one such example, as stated in a previous post.
I've done some research on the subject previously, and there are emerging products and companies that adress this issue. I have no idea on how well they work or how well they would adress your problem.
Some links:
If you're looking at Linux and various flavours of Unix you might find better solutions, but that might also be outside your scope.
Unfortunately, the SAN concept is by many something "magic", and will be able to solve all sorts of problems. As it is now, it's not much more than SCSI devices on a network. In time, software and OSes will be "SAN" aware to take advantage of the technology. Just as it took a while to write software that was truly network aware when LAN technology became more common.
/charles