We just recently added the exception stuff to handle the cases where you're interacting with heterogeneous collections of resources. For instance, an NFL game resource and a Tournament Pick'em game resource can behave similarly in many ways, but asking for a leagues collection beneath the Tournament Pick'em game resource wouldn't make any sense because there's no such thing as leagues in Tournament Pick'em. It's in those sorts of cases where we're trying to throw recoverable exceptions, where we just note that there was a problem in the <exceptions> block, instead of just killing the request entirely, which is what we would have done previously.
Basically, if you see that, you should just interpret it to mean that you're trying to get data that doesn't make any sense, but we're still doing our best to give you something reasonable. For instance, in your request, you're checking on a user who's played the following games:
107: Premiership in 2004
138: Premiership in 2005
159: Premiership in 2006
178: Premiership in 2007
205: Premiership in 2008
228: Premiership in 2009
241: World Cup in 2010
246: Premiership in 2010
261: Premiership in 2011
My goodness, that's a lot of soccer. But the general idea is that none of these games support asking for "leagues". In fact, none of these games are currently supported by the webservices, as we've only really gotten the draft & trade games (NFL, MLB, NHL, and NBA) and Tournament Pick'em enabled so far.
