What I don't understand is why you (and a lot of other people) just expect S-expression parsers to not have the exact same problems.
Now, S-expressions as used for programming languages such as Lisp do have numbers, but again Lisp has bignums. As for parsers of Lisp S-expressions written in other languages: if they want to comply with the standard, they need to support bignums.
If types other than string and a list bother you, why don't you stick with those types in JSON?
I'd be happy to use s-expressions instead :) Though to GP's point, I suppose we might then end up with JS s-expression parsers that still treat ints and floats interchangeably.