Not really. A websocket is "just" a TCP connection.
If the API provider is using a language+framework that can't easily handle lots of concurrent TCP connections, then yes, that could cause scaling issues, but... that's a choice.
There are plenty of ways to build scalable socket servers, and it's especially feasible in languages like Go and Elixir.