That's fishy. A _ConcurrentModificationException_ is not thrown (only) by access by a different thread but because of reentrant use, so this fix could be hiding a more complex problem.
Although it could be a valid fix too :) Just wondering if you investigated the cause, as I think it's very unusual to need a synchronized List. Could use a Vector as well?