To be fair unless you are specifically using the seam-pdf functionality then there's no real dependency between seam and jasper. There is a dependency between iReport and Jasper but it all comes down to the version of Jasper you choose.
My app doesn't use seam-pdf, all our reports are designed through iReport and then compiled and wared up with the rest of the app. So seam has no part in our reporting infrastructure.
So, I think before you worry too much about versions and all that decide how you are going to do your reports from an infrastructure point of view.
With regards to what jars...look at some Jasper examples it should be pretty straight forward.
I am a big Maven fan, especially to figure out dependencies. Eclipse has a very useful plugin for maven. Even if you don't want to develop/build, you can use Maven for a simple dependency task, You crate a almost empty project and define the JasperReport version you want. Maven will figure out all the dependencies for you.
Concerning Seam: You should update to Seam 2.2.2.Final because it solved an important security issue.