While in an RDBMS system you more think about the data how is in a best structure, so it is about the Schema design not about the usage, usually with such technologies like mongoDB you more have to think about how the data will be used. Of course you have to consider consistency but more need to think about to store those data together what will be needed in the same time.
Anyway it is not a good idea to do a several levels of embedded lists why it will be a pain to manage, and has some limitations.
For example like here in stackoverflow, the question is viewed along with the answers, and also with comments. These are first level lists so no problem. You do not see just the first couple of comments so if you store them for example the first 4 along with the answer and all the others in a separated collection it will work while you click to view more.
Moreover, if we go from the view where the questions listed. You start with click on the question then you query the comments and the answers (so they can be separated collections) and if somebody likely to dig deeper can click on for an individual answer to show more related comments (so it can be again a separated collection.)
If you separate the collections handling will be much easier, collections will be probably not much bigger than putting them together. You will gain extreme much on that you only have to query (page in or keep in memory) data when it is really needed to view.