Yes, I am also facing the same problem. The reason I found is:

• When WebRTC gathers ICE candidates, it doesn't just find one path—it tries to discover all possible network paths for media connectivity.
• Each entry you see corresponds to a different ICE candidate, and WebRTC generates multiple candidates for several reasons:

So, that behavior is expected :)