We have a web application deployed to Websphere 6.1.0.19 on Windows. We occasionally see this ConcurrentModificationException on a few of our reports. We are using JasperR
This is caused by the backing store of the iterator being altered while the iterator is in use. This is not a concurrency problem related to threading, as it is easy enough to do on a single thread as well.
More detailed description on this question
Your biggest problem now will be if it is fixable by you or a bug in the Jasper code.
JasperReports is now on version 3.5, so it may be worth checking whether changes post 2.0.5 (your version) have addressed any threading issues. That obviously won't resolve your current production issue, but a rebuild with the new version might.
Having said all that (and not being familiar with JasperReports) I would suspect client-threaded code.