As gellyfish mentioned, it would really help to see what you're trying to end up with after serialization.

Personally, because of the type of information I typically deal with, I ended up writing a custom serializer, but it took me a few weeks to wrap my head around how SOAP::Lite's SOAP::Serializer worked. (and I had to rewrite many functions, because they were falling functions directly, not as methods, so I had to override all of the functions which called the functions I was trying to replace).

Anyway, there is a lot of good information about using SOAP::Data at Majordojo.com, which is the personal website of the current maintainer of SOAP::Lite. You'd probably be interested in the entry on arrays of objects

You can also get a lot done simply by blessing your object to the correct data type. (it won't solve all issues, however, which is why it's necessary to see what you'd want the resulting XML to look like).