Rule #1 of system log files

Don't look at them unless you're trying to solve a specific problem

Rule #2

Log lines almost always need to be taken in context

Rule #3

They can be wrong, misleading, inaccurate or irrelevant, or all of the above

Worked example:

The "Dictionary" in your log line above isn't the kind of dictionary in which you look up the meanings of words. Well, it could be, but I'll bet a pint that it isn't.

http://stackoverflow.com/questions/7156835/what-is-an-nscfdictionary
https://developer.apple.com/library/ios/documentation/Cocoa/Reference/Foundation/Classes/NSDictionary_Class/Reference/Reference.html

The general failure of the computing public to heed these rules is why those "remote support" phone scammers do so well. They get people to open the Event Viewer on Windows systems that are working perfectly satisfactorily, and of course it's full of things that are ERRORS and WARNINGS and OMGDEVILWORDS, so why yes I will give you my IP address and get you to log in remotely to "clean up" and bill me $200 for the privilege.

The Console in OS X is no different.

Have scanned both and see they are worth perusing until some grokking gels. Yes, I see that my 'fix' as does seem ~often to STOP the leaking stenographic-pool(?!)
is not even a tame wild-goose chase.
See that NSDictionary is a cascading class of (apparently multiply-useable?) procedures by a plethora of possible clients, nor Could one 'sleuth' from
the stark form of any failure whose error-message involves 'leaking pools' (as can be only 'memory' disappearing--which Shouldn't be.)

(I have blind-hopes that something~like 'about:config' shall inhabit the new-New Mavericks/Safari gussying-up..)
Ex: When I command 'reopen last-session windows' I want it to load Only minimal stubs/or just links; NOT steal all that memory.
I'd also like granularity re that reload command: like several categories maybe by date or name. (Hah..)

I 'read' the log files periodically or natch, when there Is a glitch or seeming-one. I have taken your (and others') advice not-to imagine they are revealing [er, RAW] of much that a non-coder can use
(this century anyway.. there was a time.. assembler.. CDC-6600.)

As to letting ANYBODY (on a cold-call Fershure) into the Family Jewels, I judge that such folk must be those still stuck in, ..where's the 'any' key I'm supposed to strike?
ie Before I'd allow remotes of any ilk deliberate access, I'd have to Know Them, their daughters ages' and hobbies and arrest records.
If you're not paranoid, you'll be pwned in a trice, I comprehend.

At least, though--one Can deduce via real English a few things by comparing 'normal' messages with Weird new ones--at times; at the least: OS X fixing-self? or blaming Safari specifically.
This makes OS X a marvel of clarity compared with ..you know.
Thanks again for another useful clarification.

Welcome to IWETHEY!