Another way is to store as a List or Map. Except for the simplest of JSON, a JSON is either a List (Array) containing Lists and Maps, or a Map (Object) containing Lists and Maps. I routinely store JSON in this way, and it all goes into a single Bin.
If you are a Java programmer and use JSON Simple from Google or a C# programmer and use System.Json, the JSON Array in both implementations implement the List interface and are easily and directly stored as a List Bin. The JSON Object implements the Map interface in Java and the iDictionary (i think) interface in C# and are easily stored in a Map Bin.
The storage part is easy, but as Manigandham has mentioned, the real meat of your question is how you want to retrieve the data in the document. In the NoSQL world, the key to the data model is how you plan to retrieve the data, and there are always different ways to slice and dice the problem.
You could store your JSON as a complex data type (Compound Lists and Maps) and denormalize some attributes of data to individual bins for secondary indexed queries.
Hope this helps.