On the nightly version of Slicer, you can reproduce this bug by opening the python interactive console and entering:

f = slicer.vtkMRMLAnnotationFiducialNode()
f.SetFiducialCoordinates(0,0,0)
slicer.mrmlScene.AddNode(f)

Upon exiting, a whole bunch of VTK memory leaks will be reported:

vtkDebugLeaks has detected LEAKS!
Class vtkSynchronizedTemplatesCutter3D has 3 instances still around.
Class vtkTransformPolyDataFilter has 3 instances still around.
Class vtkInformationVector has 63 instances still around.
Class vtkMatrix4x4 has 6 instances still around.
Class vtkCoordinate has 6 instances still around.
Class vtkPlane has 3 instances still around.
Class vtkInformation has 75 instances still around.
Class vtkSynchronizedTemplates3D has 3 instances still around.
Class vtkActor2D has 3 instances still around.
Class vtkRectilinearSynchronizedTemplates has 3 instances still around.
Class vtkDoubleArray has 15 instances still around.
Class vtkAlgorithmOutput has 3 instances still around.
Class vtkInformationIntegerValue has 54 instances still around.
Class vtkOpenGLPolyDataMapper2D has 3 instances still around.
Class vtkGridSynchronizedTemplates3D has 3 instances still around.
Class vtkCutter has 3 instances still around.
Class vtkInformationExecutivePortVectorValue has 3 instances still around.
Class vtkContourValues has 15 instances still around.
Class vtkTransform has 3 instances still around.
Class vtkStreamingDemandDrivenPipeline has 6 instances still around.
Class vtkTimerLog has 3 instances still around.
Class vtkInformationExecutivePortValue has 3 instances still around.