This is 100% not the case. Eg I use a vector database of embedding to store an embedding of every video frame which I later use for matching.
There are many NLP-only related tasks this helps for but equally as many that still require lookup and retrieval.
The GPT-4 paper even has an example of this exact approach. See section 2.10:
The red teamer augmented GPT-4 with a set of tools:
• A literature search and embeddings tool (searches papers and embeds all text in vectorDB, searches through DB with a vector embedding of the questions, summarizes context with LLM, then uses LLM to take all context into an answer)
• A molecule search tool (performs a webquery to PubChem to get SMILES from plain text)
• A web search
• A purchase check tool (checks if a SMILES21 string is purchasable against a known commercial catalog)
• A chemical synthesis planner (proposes synthetically feasible modification to a compound, giving purchasable analogs)
EDIT: Another solution would be to store the session logs separately, and before each session use "fine-tuning training" to train it on your particular sessions; that could give it a "memory" as good as a typical therapist's memory.