This seems to occur particularly when a small number of events have been analysed. Many of the multiple copies are identical, but there always seems to be at least two different reports. Some of the leaks are common to both reports, but not all. The simplest solution seems to be to run over more events - I have never had multiple reports for 100 or more events. If not try using 'srtglimpse' to locate the offending code.
Output is a list of files in which 'string' occurs.
It is appropriate to reference the location of the relevant leak report for use of the responsible package co-ordinator. See section on looking at leak reports for suggested location of reports. Keep track of posted remedy reports.