Creating new WebRTC peer connections for every operation is inefficient and can lead to several issues:

• Resource overhead: Each peer connection consumes system resources and network bandwidth.
• Connection establishment delay: Setting up a new peer connection takes time due to signaling and ICE candidate gathering.
• Potential memory leaks: If connections aren't properly cleaned up, they can accumulate and cause performance issues.

Instead, use a connection management approach where you:

• Create peer connections once and store them in a dedicated manager class or object
• Handle connection lifecycle events (disconnection, errors, cleanup)
• Reuse existing connections when needed
• Properly clean up connections when they're no longer needed