Have a look at multi-instance characteristics (see userguide). This allows you to repeat a single service-task multiple times, based on a collection of values. These values can be stored as a process-variables, based on a step before or just based on an expressions which resolves to a service-call.
The tricky part is to connect the right "behaviour" to the service-task invocation.
Another alternative is to just execute the JavaDelegate from within the code (as you whould call any code) or event call your own interface-methods on each of the different operations you want to perform. This will only show one service-task in the history offcourse, so not as optimal as the multi-instance approach, which can even be made asynchronous.