Release browse requests, or any type of request that returns a list of releases, can currently return a nearly-unbounded number of tracks. Due to the amount of processing required to load and create so many objects on the server, this can cause the request to time out, almost certainly so if additional inc parameters are specified for the tracks (recordings, artist-credits). This is particularly troublesome for endpoints like /ws/2/discid which can be provided with a very large TOC to return releases for.
I'd propose to limit the number of releases returned in these requests such that the total number of tracks doesn't exceed some sane limit, like 500. We should always return at least one release (and never partially), but stop once the number of tracks exceeds 500.